Fix/quest sdk no boundary #737
Conversation
There was a problem hiding this comment.
The manifest parts look good (edit: I thought it looks good, but it didn't actually work. Type mismatches). I know we shouldn't look too carefully at Unity files, but normally it's just additions -- here there were some things that seem to have been removed or disabled. Deliberate?
Also, I'd like to test an upload for Quest on this branch -- any objections if I push a commit, later to be reverted, to try this?
|
All the changes in the Unity files were by Unity - I didn't change anything manually except updating the package version |
|
I'm going to try reverting the changes to those files locally to see if the new sdk automatically makes the same changes again. |
|
ok. Also note that the Mac failure was a real failure, but perhaps we just need to delete the package cache |
|
The Mac failure is real, but I think we should probably just be removing the package on Mac |
No description provided.